home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
tex-k-archive.gz
/
tex-k-archive
/
000293_neal@ctd.comsat.com_Wed Feb 9 05:09:00 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-11
|
3KB
Received: from neal.ctd.comsat.com by cs.umb.edu with SMTP id AA21919
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Wed, 9 Feb 1994 10:09:08 -0500
Received: by neal.ctd.comsat.com (Smail3.1.28.1 #29)
id m0pUGXL-0002fOC; Wed, 9 Feb 94 10:09 EST
Message-Id: <m0pUGXL-0002fOC@neal.ctd.comsat.com>
Date: Wed, 9 Feb 94 10:09 EST
From: neal@ctd.comsat.com (Neal Becker)
To: kb@cs.umb.edu
Cc: tex-k@cs.umb.edu
Subject: Re: Engine specific font paths
In-Reply-To: <199402091232.AA03727@terminus.cs.umb.edu>
References: <199402091232.AA03727@terminus.cs.umb.edu>
Here is an example of a config file for eps:
---------------------------
"Panasonic KX-P1080" | EpsonMXFX {
engine = "EpsonMXFX"
vpins = 8
dpih = 240
dpiv = 216
graphicsmode = "\eZ"
vskip = 216
vinc = 1
hinc = 2 # 2 passes should look better
vinterleave = 3 # pin spacing is 1/72 inch = 3/216
resetstring = "\e@"
UseEscF0
minskipspaces = 5
vspread = 1
vaddvstr = "\eJ%c"
}
EpsonMXFX-low {
engine = epsonlo
vpins = 4
dpih = 120
dpiv = 108
graphicsmode = \e L
vskip = 216
vinc = 1
hinc = 1
vinterleave = 3
resetstring = "\e@"
UseEscF0
minskipspaces = 5
vspread = 2
vaddvstr = "\eJ%c"
}
NEC {
engine = NEC
vpins = 24
dpih = 180
dpiv = 180
vskip = 180
graphicsmode = "\e*\x27"
vskip = 180
vinterleave = 1
vaddvstr = "\eJ%c"
}
NEChi {
engine = NEChi
vpins = 24
dpih = 360
dpiv = 360
graphicsmode = "\e*\x28"
vskip = 360
vinterleave = 2
vaddvstr = \x1c\x33 "%c" \x0a
}
--------------------------------------------
To find fonts for a particular 'engine' we consult the 'fontdesc' file
(this is standard part of mctex lib)
--------------------------------------------
font pk EpsonMXFX 3 /usr/TeX/lib/tex/fonts/EpsonMXFX/%f.%mpk
font pk epsonlo 3 /usr/TeX/lib/tex/fonts/EpsonMXFX-lo/%f.%mpk
--------------------------------------------
Now to make fonts with MakeTeXPK I modify the MakeTeXPK. In many
implementations of MakeTeXPK there is a 6th optional arg specifying
what subdir the fonts should go into. I modify this so that this can
be either a subdir or an absolute path. The idea is that I already
had to specify the font path to the driver in fontdesc - it's crazy to
require the user to specify it again in MakeTeXPK.
This implementation is similar (in principle) to dvips - I specify
device-dependent info in a config file. I use a single config file
for all printers as opposed to seperate files for each - but that's
not important.
What *is* important is that having already needed to specify the font
path in a device specific config file I shouldn't need to ever specify
it again anywhere else. So I recommend that drivers call MakeTeXPK
passing this info.
Here is the mod I make to MakeTeXPK to use the optional 6th arg:
------------------------------
if test "$6" != ""
then
case "$6" in
/*) DESTDIR="$6" ;;
*) DESTDIR=$DESTDIR"/$6"
esac
if test ! -d $DESTDIR
then
mkdir $DESTDIR
fi
else
DESTDIR=$DESTDIR"/$MODE"
fi